home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The World of Computer Software
/
The World of Computer Software.iso
/
fmv104.zip
/
FMSVER.DOC
next >
Wrap
Text File
|
1990-07-07
|
8KB
|
211 lines
FMSVER v1.04 - July 7, 1990
PURPOSE:
-------
To verify that files listed in your RBBS-PC FMS directory actually exist,
and to update file sizes accordingly.
USAGE:
-----
FMSVER <input.fil> <output.fil> <trashcan.fil>
CONFIGURING FMSVER:
------------------
The first time FMSVER is run, it will walk you through it's configuration.
When finished, the configuration file FMSVER.CNF will be in the default
directory. This file MUST be present in order to run FMSVER against your
FMS directory(s). To create this configuration file, you will need to
know up front:
- the number of download directories in your system,
- their names,
- the path/filename of your FMS directory, and
- the path/filename of the output file that FMSVER will create.
The filenames can be changed from the command line (see next section),
but FMSVER will ALWAYS use the subdirectories listed in the configuration
file for it's searches.
Do not specify the same file for both input and output!
The output file will be a valid FMS directory, consisting of all files
that were listed in your current FMS, and were physically found in one
of the directory(s) you specified.
The "Trashcan" file will also be a valid FMS directory, and will consist
of all files that were listed in your FMS, but were not found in the dirs
you specified. This file defaults to "NOTFOUND.TXT" in the current DOS
subdirectory. The only way to specify a different file name for the
trashcan is to use the command line option.
A copy of my FMSVER.CNF file is included in this package as SAMPLE.CNF.
THE COMMAND LINE OPTION:
-----------------------
You can supply the input, output, and trashcan filenames (respectively)
on the command line, which will bypass what's listed in the configuration
file. If nothing is supplied on the command line, it will take the file
names from the configuration file, and the trashcan will be named
NOTFOUND.TXT in the current directory.
The command line option lets you run FMSVER from a batch file to process
multiple FMS directories, such as:
fmsver mstr88.dir mstr88.fix trashcan.88
fmsver mstr89.dir mstr89.fix trashcan.89
^ ^ ^
| | |
NOTE that there can only be ONE blank space between these arguments if
you decide to use the command line option.
If an invalid filename is supplied, FMSVER will error back to DOS. If
the output filename isn't specified on the command line then you'll be
prompted for it.
Again, typing FMSVER by itself will cause it to go to the configuration
file for the input and output file names, and the "trashcan" file will
always be NOTFOUND.TXT.
CHAINED DIRECTORIES:
-------------------
If "\FMS CH" is found as the first seven characters on the line, then it
will be written to the output file. This line will NOT be written to the
trashcan file.
EXTENDED DESCRIPTIONS:
---------------------
Extended descriptions are optional in RBBS-PC, and are as such optional
as far as FMSVER is concerned. If they exist, they are treated in one of
two ways:
- "FMS Standard method" (for lack of a better term) is how RBBS and
FMSVER treat the FMS by default (Bottom-to-top order):
Extended 4 ...
Extended 3 ...
Extended 2 ...
Extended 1 ...
FILENAME.EXT ...
- "\FMS TOP method" (also for lack of a better term) is a directive
that can be given to RBBS and FMSVER instructing them to read the
FMS directory as a straight text file (top to bottom order). If
the first character of any line in the FMS is a backslash, *AND*
the string "FMS TOP" appears anywhere on that line, the FMS is
handled in straight top-to-bottom order thereafter. In this case
the extended descriptions are treated as:
FILENAME.EXT ...
Extended 1 ...
Extended 2 ...
Extended 3 ...
Extended 4 ...
After glancing through the RBBS docs, I found that 4 extended description
lines are supported, so that's what FMSVER can handle. If there are more
than 4 extended description lines for any given filename, lines 5 and
beyond will not be written to the output file.
PRIVATE FILENAMES:
-----------------
RBBS supports private filenames in your FMS directory, which are preceeded
by an equals '=' sign. If FMSVER finds an equals sign as the first character
on the line, it is handled as such, and it's info will be written to the
appropriate output file.
FMS COMMENT LINES:
-----------------
If RBBS finds an asterisk '*' or a backslash '\' as the first character
on any given line of your FMS, they are treated as public or private
comments respectively. If any line in your FMS begins with either of these
two characters, FMSVER will write the line to your output file immediately,
and proceed to the next line. A couple of important notes here:
- If either of the two types of comment lines are imbedded inside of an
extended description, the comments may not appear in your output file
in EXACTLY the same place as they were originally. (They will be either
just before or just after the extended description for that file).
- Also, these comment lines will NOT be written to the trashcan file in
any case.
FILE SHARING:
------------
I run a 3-node netbios lan under DOS Share, so file sharing was VERY
important to me when writing this program.
The FMS directory being verified is opened in a shared fashion, which
means that someone can be online on another node listing your directories
while FMSVER is running. The files listed in your FMS are also temporarily
opened and closed in order to both check for their existence, and to
determine their size. With that in mind, they are also opened in a shared
fashion, so it is up to your download protocals as to whether or not they
will be sharable if someone is downloading one on another node when FMSVER
finds it.
FMSVER requires DOS version 3.00 or later for the above reasons. You do
NOT have to be running a network to use FMSVER.
~~~
WHAT'S NOT SUPPORTED?
--------------------
If you find anything, let me know!
DISCLAIMER:
----------
It works for me, and I hope it works for you. Beyond that, no warranty
either expressed or implied.
SEMI-SHAREWARE:
--------------
If the program works for you, use it and pass it around. If you REALLY
appreciate it, feel free to send a few dollars to:
Chip Morrow
The Newark Connection RBBS
P.O. Box 2023
Heath, OH 43056
If $10 or more, I will send you a copy of the QB source, and the latest
version on a 5 1/4" disk. (Sorry, no 3 1/2" drives in the house).
Note - The source requires QB 4.xx, Crescent Software's PDQ library, and
Tom Hanlin's ADVBAS in order to recompile the code unmodified.
BUGS, UPDATES, ETC.
------------------
FMSVER1, 2, and 3.ZIP - My first three tests of the program, with a big
THANKS to Randy Sun for all the testing and feedback!
FMSVER4.ZIP (1.00b) - Added support for different trashcan file names
via the command line.
1.01b - Fixed a nasty EOF bug in FMSVER4.ZIP that was causing input
past end of file.
1.03b - Added support for FMS TOP, and upped the maximum number of
download directories to 20.
1.04 - First non-beta release. Added support for private files and
both public and private FMS comment lines.
Would appreciate any comments, suggestions, etc. I can be reached via
modem in one of three ways:
- Compuserve Easyplex to user #72677,502 (Chip Morrow)
- RBBS-PC (mail addressed to SYSOP) at 614-366-4392.
- Netmail addressed to Chip Morrow at RBBS-NET address 8:965/9.